#systems analysis (11)
Event Storming Without the Hype: Pros, Cons, and a Sticky Note on Your Forehead
A personal take on Event Storming after more than one "event storm": where it genuinely saves a team, where it turns into pointless sticker-therapy, and what it takes to keep a session from going down the drain.
The More Detailed the Spec, the Weaker the Developers — A Paradox I Keep Seeing on Projects
Why overly detailed requirements erode developer expertise over time, where the real pros and cons of a high-level spec lie, and how to strike a balance between predictability and team growth.
Classic Mistakes Systems Analysts Make on IT Projects
Typical missteps systems analysts make on large enterprise projects in banking and fintech: vague requirements, legacy integrations, regulation, negative scenarios and early validation — and how to cut the risk ahead of time.
Data Exchange Formats: From JSON to Protobuf
A deep dive into data exchange formats: where JSON lives, why XML still matters, what makes YAML great, and when it is time to switch to binary Protobuf, Avro, and MessagePack — tied to APIs and message brokers.
UML: what kind of beast is it, and why analysts steer clear
UML can visualize, specify and document a system — yet you almost never see it used on real teams. Let’s figure out what it’s for, why analysts avoid it, and where it actually pays off.
Microservices or Monolith?
A cheat sheet for choosing an architecture: the pros and cons of monoliths and microservices, what works better for a small company, what level of engineers you need, and a checklist to help you pick an approach.
User Stories: The Most Underrated Thing on Teams
What a user story actually is, how to write one using the "who — what — why" formula, why acceptance criteria matter, and the traps teams fall into most often.
SQL in Practice: Installing PostgreSQL and Writing Your First Queries
A hands-on SQL guide for analysts and IT specialists: install PostgreSQL locally and write your first queries — from CRUD and JOINs to aggregates and transactions.
Analysts and Their Many Flavors
Who an analyst actually is in IT and what specializations exist: a tour of 18 kinds of analyst — from business and systems to Data Scientist — plus salary ranges and why the field has real upside.
How to Interview a Client When You're the Analyst on an IT Team (a Checklist)
A step-by-step algorithm for interviewing a client when there is no business analyst on the team: preparation, running the interview, analysis, and confirming requirements.
Word of the Day — Idempotency
A quick primer on idempotency: what this property of operations is, why it matters for system reliability, and where it shows up — from HTTP methods to databases and blockchain.